Skip to content

Conversation

@mikatammi
Copy link
Contributor

@mikatammi mikatammi commented Aug 1, 2025

Did some investigation from Botan sources to really check how things work. pwdhash function seems to take arguments in a different order than what pwdHashTimed returns, when using Argon2 and Scrypt KDFs.

Also changed the names i, j, k to more descriptive ones: iterations, parallelism, memoryParam

There is open issue about this open since 2019:
randombit/botan#2144

* Fix parameter ordering for Scrypt and Argon2 testcases
* Change i, j, k to more descriptive names of the parameters
* Add comments where to find the parameter orders from Botan's C++ code

Signed-off-by: Mika Tammi <mikatammi@gmail.com>
@mikatammi
Copy link
Contributor Author

I have questions based on the comments that already exist in the PwdHashSpec.hs:

@jorisdral
Copy link
Collaborator

Thank you for the PR! I might need a little more time to get familiar with the code myself to review your changes and to answer your questsions, but the fixes are most appreciated.

@jorisdral
Copy link
Collaborator

I included your changes in PR #63. Thanks for your contribution!

@jorisdral jorisdral closed this Oct 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants